Skip to main content

This is a new service – your feedback will help us to improve it.

Maidstone Borough Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

16/1976

reference
TPO704
name
16/1976
tree-preservation-order

undefined

16/1976
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((0.592214 51.292898,0.592291 51.292900,0.592607 51.292934,0.592724 51.292956,0.592896 51.293038,0.592657 51.293077,0.592113 51.293074,0.591752 51.293133,0.591499 51.293199,0.591412 51.293231,0.590783 51.293418,0.590701 51.293521,0.590628 51.293694,0.590621 51.293773,0.590648 51.293865,0.590712 51.293981,0.590770 51.294113,0.590825 51.294170,0.590877 51.294208,0.591018 51.294217,0.591149 51.294214,0.591237 51.294224,0.591315 51.294249,0.591466 51.294153,0.591625 51.294078,0.591942 51.293987,0.592024 51.294030,0.591824 51.294121,0.591557 51.294288,0.591398 51.294524,0.591331 51.294489,0.591238 51.294454,0.590919 51.294393,0.590797 51.294381,0.590622 51.294304,0.590552 51.294254,0.590503 51.294204,0.590463 51.294132,0.590391 51.293956,0.590350 51.293811,0.590341 51.293711,0.590360 51.293628,0.590399 51.293557,0.590476 51.293465,0.590586 51.293362,0.590781 51.293229,0.590888 51.293168,0.591091 51.293079,0.591292 51.293011,0.591588 51.292945,0.591773 51.292925,0.592214 51.292898)))
point
POINT (0.59125 51.293612)
notes
Maidstone Borough Council Tree Preservation Order No. 16 of 1976 under Section 60 of the Town and Country Planning Act 1971. Area of Trees - A3 comprising Ash (Fraxinus excelsior),
organisation
entry-date
1976-07-12
start-date
1976-07-02
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Maidstone Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL